-
Notifications
You must be signed in to change notification settings - Fork 28
add spell check to markdown files #239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
install: | ||
- npm i -g markdown-spellcheck | ||
before_script: | ||
- wget --quiet https://gist.githubusercontent.com/juancarlostong/dad02feeebc8763af35b4fdc717cf7a2/raw/29e085302a9418edbefba15d8f790fa76e0a89d5/.spelling |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
opting for a simple wget rather than the more expensive cloning of an entire repo. we only need this one file anyway and there's no secrets in it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it have to be node? Is there a more performant platform we can use?
Also, I'd prefer if we can run this in parallel to the other stages so we don't have to wait for it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if this PR looks good, i will create similar PRs on all the remaining SDK repos |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! I have some questions below, not blocking though.
install: | ||
- npm i -g markdown-spellcheck | ||
before_script: | ||
- wget --quiet https://gist.githubusercontent.com/juancarlostong/dad02feeebc8763af35b4fdc717cf7a2/raw/29e085302a9418edbefba15d8f790fa76e0a89d5/.spelling |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it have to be node? Is there a more performant platform we can use?
Also, I'd prefer if we can run this in parallel to the other stages so we don't have to wait for it
Summary
This is what it looks like when it finds a spelling error (aborts build):
https://travis-ci.org/optimizely/ruby-sdk/jobs/647067279